home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Chip 1998 September
/
CHIP NET Rehberi Eylül 1998.iso
/
ftp
/
gbxwind2p6
/
DATA1.CAB
/
Example_Files
/
README.TXT
< prev
next >
Wrap
Text File
|
1998-05-13
|
11KB
|
248 lines
-----------------------------------------------------------------
Gigabyte Express for Windows(x86) Version 2.6
Demo - Floppy P/N 0.1451, self extracting form P/N 0.1452
Release - Floppy P/N 0.1446, self extracting form P/N 0.1453
Copyright (c) 1995-1998
Niwot Networks, Inc., Boulder, CO. May 7, 1998
Voice: (303) 444-7765
Fax: (303) 444-7767
email niwotnet@aol.com
web http://www.niwot.com
This README.TXT has information on release 2.6 of
Gigabyte Express for Windows(x86).
This code inter-operates with Gigabyte Express for the Macintosh
(4.4 and higher) as well as Gigabyte Express for Windows (Alpha).
The DEMO code may be used with serial numbers niwotdemo1(default),
niwotdemo2, or niwotdemo3.
DEMO Code expires 9/1/98.
If you want to use Macintosh compatible files then we recommend
installing in a Mac volume on an NT server; that way files will
be directly viewable from your Macintosh.
FIXES AND ENHANCEMENTS SINCE RELEASE 2.5:
1. Improved disconnect processing, which sometimes left remote
side in "Disconnecting" state or in "Waiting for Call" state but
unable to accept incoming calls.
2. Corrected problem with empty folders in the outgoing list of
files/folders generating "Unable to open file" errors.
3. Corrected failure of Win95 to display files in Send Files window
when archive bit is turned off.
4. GBXWin now remembers size and position of application windows.
5. A Log Window was added to provide on-screen reporting of activity.
This window is enabled/disabled with the "View/Log Window" menu item.
6. Autosend now supports a [NoFolder] option, which prevents autosend
from expanding or sending any folders within the source folder.
7. GBXWin Log changes: time/date stamp was modified to supply 4-digit
year, and destination folder is displayed when receiving a file.
KNOWN ISSUES TO BE ADDRESSED IN THE FUTURE:
1. Answer sessions may continue attempting to listen on IP
addresses which are no longer are valid on your machine;
you may have to edit "transport" to re-select an address on
which to listen.
2. Problems can occur if more than 4 sessions of a type are
defined (a fifth Answer session, for example).
3. The Log Window must be closed using the "View/Log Window" menu
item (the Close button on the window itself will not work).
-----------------------------------------------------------------
-----------------------------------------------------------------
Gigabyte Express for Windows(x86) Version 2.5
Demo - Floppy P/N 0.1451, self extracting form P/N 0.1452
Release - Floppy P/N 0.1446, self extracting form P/N 0.1453
Copyright (c) 1995-1998
Niwot Networks, Inc., Boulder, CO. March 6, 1998
Voice: (303) 444-7765
Fax: (303) 444-7767
email niwotnet@aol.com
web http://www.niwot.com
This README.TXT has information on release 2.5 of
Gigabyte Express for Windows(x86).
This code inter-operates with Gigabyte Express for the Macintosh
(4.4 and higher) as well as Gigabyte Express for Windows (Alpha).
The DEMO code may be used with serial numbers niwotdemo1(default),
niwotdemo2, or niwotdemo3.
DEMO Code expires 7/1/98.
If you want to use Macintosh compatible files then we recommend
installing in a Mac volume on an NT server; that way files will
be directly viewable from your Macintosh.
FIXES AND ENHANCEMENTS SINCE RELEASE 2.4:
1. Added error notification on both sender and receiver when problems
occur at end of file transfer (such as error renaming temp file).
2. Removed case-sensitivity in detection of autosend list filenames.
3. Cleared inaccurate display of throughput and remaining time after a
"Get" is completed.
4. Corrected problem replacing existing files when running on Win95 and
receiving to a Novell server.
5. Corrected problem when outgoing list of files/folders contains empty
folders; siblings of the empty folder were sometimes skipped.
6. Added validation when entering PenName. Will not accept a value of
"Niwot_inBasket"; PenName cannot include colon (:).
7. Added reporting of current GBXWin version when opening logfile.
8. Corrected checking for duplicate serial numbers. Earlier GBXWin
versions could report a duplicate serial number when the two
serial numbers were actually different.
9. GBXMac initiated connections to GBXWin might have the Mac stay in
"disconnecting" while the GBXWin goes to idle normally.This was
corrected in GBXMac 4.8.1
KNOWN ISSUES TO BE ADDRESSED IN THE FUTURE:
1. Answer sessions may continue attempting to listen on IP
addresses which are no longer are valid on your machine;
you may have to edit "transport" to re-select an address on
which to listen.
2. Connection attempts may fail, leaving the answering side
unable to accept new calls but saying "WAITING FOR CALL".
This situation can be corrected by exiting and restarting
the application.
3. Problems can occur if more than 4 sessions of a type are
defined (a fifth Answer session, for example).
-----------------------------------------------------------------
-----------------------------------------------------------------
Gigabyte Express for Windows(x86) Version 2.4
Demo - Floppy P/N 0.1451, self extracting form P/N 0.1452
Release - Floppy P/N 0.1446, self extracting form P/N 0.1453
Copyright (c) 1995-1997
Niwot Networks, Inc., Boulder, CO. February 16, 1998
Voice: (303) 444-7765
Fax: (303) 444-7767
email niwotnet@aol.com
web http://www.niwot.com
This README.TXT has information on release 2.4 of
Gigabyte Express for Windows(x86).
This code inter-operates with Gigabyte express for the Macintosh
(4.4 and higher) as well as Gigabyte Express for Windows (Alpha).
The DEMO code may be used with serial numbers niwotdemo1(default),
niwotdemo2, or niwotdemo3.
DEMO Code expires 7/1/98.
If you want to use Macintosh compatible files then we recommend
installing in a Mac volume on an NT server; that way files will
be directly viewable from your Macintosh.
FIXES AND ENHANCEMENTS SINCE RELEASE 2.2:
1. Protected the code from inbound file and directory
names (and Pen Names) which end in a space or period, or which contain
any of the characters * : < > | / \ ? "
The log shows Error Creating File (-120) or
Error Creating File or Folder (RC=-37). These show up on the
sending GBXMac as "Remote side could not find inBasket" or "Receive
Side Setup Err = 0 Rec = -37" If this error is returned to a sending
GBXWin then "Error Creating File on Remote" is reported.
2. Added support for filename wildcards in autosend.
3. Better handling of disk drives larger than 2 Gigabytes, no longer
reporting "insufficient space" since we now use 64 bit math to determine
if there is room.
4. Problems which occur while checking available disk space will
generate diagnostic log messages regardless of "Use Log File" check box.
GBXWin.log will be opened or created as necessary.
5. Added ability for Windows NT station accessing an NTFS NT server
volume to read or write the Mac-compatible streams.
6. Added warnings that Mac-compatible streams are not supported by Win95.
7. Improved error reporting when finding or creating files
or directories fails.
8. Add detailed logging when a duplicate serial number is detected
KNOWN ISSUES TO BE ADDRESSED IN THE FUTURE:
1. Answer sessions may continue attempting to listen on IP
addresses which are no longer are valid on your machine;
you may have to edit "transport" to re-select an address on
which to listen.
2. Connection attempts may fail, leaving the answering side
unable to accept new calls but saying "WAITING FOR CALL".
This situation can be corrected by exiting and restarting
the application.
3. Problems can occur if more than 4 sessions of a type are
defined (a fifth Answer session, for example).
4. GBXMac initiated connections to GBXWin may have the Mac stay in
"disconnecting" while the GBXWin goes to idle normally.
GBXMac returns to idle when either a link watchdog occurs or
the session is manually stopped.
-----------------------------------------------------------------
-----------------------------------------------------------------
Gigabyte Express for Windows(x86) Version 2.2
Demo - Floppy P/N 0.1451, self extracting form P/N 0.1452
Release - Floppy P/N 0.1446, self extracting form P/N 0.1453
Free Client - Floppy P/N 0.1465, self extracting form P/N 0.1466
Client - Floppy P/N 0.1467, self extracting form P/N 0.1467
Copyright (c) 1995-1997
Niwot Networks, Inc., Boulder, CO. October 8, 1997
Voice: (303) 444-7765
Fax: (303) 444-7767
email niwotnet@aol.com
web http://www.niwot.com
This README.TXT has information on release 2.2 of
Gigabyte Express for Windows(x86).
This code inter-operates with Gigabyte express for the Macintosh
(4.4 and higher) as well as Gigabyte Express for Windows (Alpha).
The DEMO code may be used with serial numbers niwotdemo1(default),
niwotdemo2, or niwotdemo3.
DEMO Code expires 12/1/97.
If you want to use Macintosh compatible files then we recommend
installing in a Mac volume on an NT server; that way files will
be directly viewable from your Macintosh.
FIXES AND ENHANCEMENTS SINCE RELEASE 2.1:
1. Added running estimates of transfer rate and remaining time
to visual display. Accuracy of timing was also improved.
2. Added logging of inbound and outbound IP addresses at
connection time (if logging is enabled).
3. Compression option moved from Dial window to Phonebook to
allow better control.
4. GBXWin now traps potential crashes within dialup networking
caused by incomplete dialup installation.
5. Corrected unnecessary creation of _sent folders during
autosend with newer options (e.g., "move to trash", etc.).
6. Filters added to Send Files/Folders to prevent transmission
of GBXWin temp files or Mac resource forks as data.
KNOWN ISSUES TO BE ADDRESSED IN THE FUTURE:
1. Answer sessions may continue attempting to listen on IP
addresses which are no longer are valid on your machine;
you may have to edit "transport" to re-select an address on
which to listen.
2. Connection attempts may fail, leaving the answering side
unable to accept new calls but saying "WAITING FOR CALL".
This situation can be corrected by exiting and restarting
the application.
3. Problems can occur if more than 4 sessions of a type are
defined (a fifth Answer session, for example).
-----------------------------------------------------------------